I have updated the tests.

Seems like this line is no longer required for my build, removing this line also passes the existing tests.
Npm sets flags into process.env using this piece of code. Any flag like --some-str gets set into process.env as npm_config_some_str. This might also apply to the target, runtime and arch flags.

Might be a breaking change for some peaople, leaving it as is for now.

Edit: I am ending my day, feel free to edit or add new commits. 👋

Seems like this line is no longer required for my build, removing this line also passes the existing tests.

Yeah, I'm also a little fuzzy on the precedence here, I wanna take a closer look myself.

How should it work when you have build_from_source=true in npmrc, but install with npm i --build-from-source=non-matching-package-name? That should result in false, right?

The settings from .npmrc have priority over flags passed in the CLI.
If you pass both, npm will set the env value to whatever is inside .npmrc, if this is a package name, it will only rebuild that package. If its true it will rebuild all packages.

The settings from .npmrc have priority over flags passed in the CLI.

Generally they don't. And for build-from-source that isn't true either; in node-pre-gyp the dashed command line option takes precedence over the underscored rc/env option:

var source_build = gyp.opts['build-from-source'] || gyp.opts.build_from_source

So to stay in line with node-pre-gyp, we should also modify this to support --build-from-source=x:

And move this logic accordingly:

But we can move those tasks to a follow-up PR, because it's about a separate feature. Before that, perhaps we can change (some of) the rc tests to functional tests - i.e. running npm install on a mock package.

@vweevers how can I help you merge this?

I need some more eyes on this.

5.3.0

Thanks guys, nice working with you.